forked from kubernetes/kubernetes
-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release v1.30] k8s v1.30.4 #156
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
After the introduction of v1beta4 if the user inputs the old v1beta3 discovery timeout the value is ignored. Fix that by introducing a conversion to v1beta4. Co-authored-by: penghez (GitHub handle)
This change make api-server not omity the field `item` of ValidatingAdmissionPolicyList when ValidatingAdmissionPolicy is empty. So kubetl will print ValidatingAdmissionPolicyList correctly when ValidatingAdmissionPolicy is empty. Signed-off-by: xyz-li <[email protected]>
For request like '/api/v1/watch/namespaces/*', don't set scope.namespace. Because the func `addWatcher` add a watcher to allWatchers with the value `scope.namespace` not empty. But the function `dispatchEvent` dispatch event with an empty namespace. Signed-off-by: xyz-li <[email protected]>
…k-of-#125404-upstream-release-1.30 Automated cherry pick of kubernetes#125404: Fix that PodIP field is not set for terminal pod
…k-of-#126046-upstream-release-1.30 Automated cherry pick of kubernetes#126046: Use omitempty for optional fields in Job Pod Failure Policy
During kubeadm join in 1.30 kubeadm started respecting the kubeletconfiguration healthz address/port. Previously it hardcoded the health check to localhost:defaultport. A corner case was not handled where the user applies --patches on join to modify the local kubeletconfiguration. This results in kubeletconfiguration patch target patches not being applied to the KubeletConfiguration in memory and the health check running on the address:port which are present in the kubelet-config configmap. Fix that by explicitly calling a new function to patch the KubeletConfiguration in memory. This is scoped to only handle the healthz checks *after* the kubelet config.yaml was already patched and written to disk.
This ensures that the restartable init containers receive a termination signal even if there are any not-started restartable init containers, by ignoring the not-running containers.
Signed-off-by: Marko Mudrinić <[email protected]>
…-pick-of-#126174-upstream-release-1.30 Automated cherry pick of kubernetes#126174: mount-utils: treat syscall.ENODEV as corrupted mount
…pick-of-#125480-origin-release-1.30 Automated cherry pick of kubernetes#125480: kubeadm: fix a bug in
…ry-pick-of-#125690-upstream-release-1.30 Automated cherry pick of kubernetes#125690: Fixed metrics missing issue for metrics reference page
Cherry pick of kubernetes#124568 fix ValidatingAdmissionPolicyList json tag
cherry pick of kubernetes#125145 apiserver fix watch namespace
…pick-of-#126224-origin-release-1.30 Automated cherry pick of kubernetes#126224: kubeadm: fix join bug where kubeletconfig was not patched in
…k-of-#126231-origin-release-1.30 Automated cherry pick of kubernetes#126231: Falls back to SPDY for gorilla/websocket https proxy
…ck-of-#125566-upstream-release-1.30 Automated cherry pick of kubernetes#125566: kubeadm: Add '--yes' flag to the list of allowed flags
…ck-of-#125935-upstream-release-1.30 Automated cherry pick of kubernetes#125935: Terminate restartable init containers ignoring not-started containers
…k-of-#126167-upstream-release-1.30 Automated cherry pick of kubernetes#126167: Hot fix for panic on schema conversion.
…ick-of-#126470-kubernetes-release-1.30 Automated cherry pick of kubernetes#126470: Move APIServingWithRoutine to alpha and disabled by default.
…9-to-release-1.30 Cherry pick kubernetes#122499 to release-1.30
…ick-of-#126012-upstream-release-1.30 Automated cherry pick of kubernetes#126012: Updating kubelet on Windows to query uuid from registry
chiukapoor
force-pushed
the
rancher-v1.30.4
branch
from
August 21, 2024 13:11
e88ac5c
to
f24d721
Compare
kinarashah
approved these changes
Aug 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates
vendor update
on top, as it generally requires an update during a k8s (patch or minor) version release.Issues